Update New-AzGalleryImageDefinition.md to have correct values for SecurityType #26428
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correcting one value of SecurityType inputs list from TrustedandConfidentialVMSupported TrustedLaunchAndConfidentialVmSupported
Description
The current documentation lists the values that you can be used when specifying the SecurityType of the Image Definition being created with New-AzGalleryImageDefinition. One of the options provided in the list is “TrustedandConfidentialVMSupported”, this value is incorrect and should be “TrustedLaunchAndConfidentialVmSupported” instead
If the current incorrect value listed "TrustedandConfidentialVMSupported" is used, the cmdlet will fail with the following error message:
The proper value of "TrustedLaunchAndConfidentialVmSupported" can also be seen when viewing the generated ARM template by the Azure Portal when reviewing an Image Definition that was created through the portal and selecting Trusted Launch and Confidential VM Supported as the Security type.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.